home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Power Tools 1993 November - Disc 2
/
Power Tools Plus (Disc 2 of 2)(November 1993)(HP).iso
/
hotlines
/
nethl
/
ots
/
opuskinf.txt
< prev
next >
Wrap
Text File
|
1980-01-04
|
11KB
|
282 lines
OPUSK Delta information from OPUS1
----------------------------------
Note : OPUSK corresponds to OTS C.03.00 Release
OPUS1 corresponds to OTS C.02.00 Release
New Features Include
--------------------
o APRI, an application interface to the ISO ACSE, Presentation and ROSE
layers, based on emerging standard interface.
o Fully X/Open XPG3 compliant XTI implementation. Now uses true file
descriptor endpoints (supporting fork(), select(), poll()).
o Ability to act as an Active Transport Layer Relay (a.k.a. MSDSG).
o Dynamic configuration of layer parameters and remote system
information.
o Statistics library for access to per connection and per layer
information.
o OTS/9000 resides in kernel and uses the streams architecture,
providing improved performance. Preliminary results show 80% peak
throughput increase versus previous release (through XTI, over LAN on
S835).
o Available tracing of data and header information at each layer (2 -
7) of stack.
o API tracing, which allows a process using the XTI, Session or APRI
interfaces to trace its calls to the API.
o Ability to start/stop X.25 cards while stack is running.
o Improved per destination facilities control.
o Up to 448 connections LAN connections.
o Support for one or two LAN cards.
o Support of S700 platform.
o Support for FDDI when released.
ACSE/Presentation and ROSE Interface
------------------------------------
OTS/9000 includes APRI which provides a programmatic interface(API)
in C. This interface is based on the UNIX International OSI
ACSE/Presentation Library specification draft of October 1990.
The emerging X/Open interface at these layers is derived from
this specification, but was not finalized at the time of
product release.
Through this interface you can establish associations (connections)
with another application process, send and receive data, and
shutdown associations. The ROSE services may be used to in
conjunction with the ACSE/Presentation services to perform
ROSE request/reply operations.
X/Open Transport Interface
--------------------------
XTI endpoints are now true UNIX file descriptors and can be inherited
by child applications. The XTI Programmer's Guide discusses other
changes in detail.
Dynamic Routing Commands
------------------------
OTS now provides tools to examine and modify known destination
systems. The commands are otsaddes(1M), otsdeles(1M) and
otsshowes(1M). Similar commands also exist for performing
these operations for intermediate systems and routers.
These commands are described in Chapter 5 of the "Installing
and Administering OTS" manual.
Statistics Library
------------------
Applications can use the Statistics Library interface (in C) for
determining the information such as the number of connections
available or currently made through a particular layer, and the
amount of data sent and received over a particular connection.
This interface is described in Chapter 8 of the "Installing
and Administering OTS" manual.
Tracing and Logging
-------------------
OTS now uses the HP standard trace and log tools nettl(1M) and
netfmt(1M). The tools "otstrace" and "otsfmt" are no longer
supported. The tracing and logging mechanism is described
in detail in Chapter 6 of the "OSI Planning and Troubleshooting
Guide".
API Tracing
-----------
The API tracing facilities are provided to aid in debugging
applications built using the OSI API's. This tracing facility is
distinct from the tracing and logging provided by nettl(1M).
Whereas nettl(1M) tracing is intended to show you actual PDU's and
other protocol specific information passing through the system,
API tracing shows you library calls and arguments issued by your
application to the API it is linked with.
Through API tracing you can quickly verify that your application
is calling the API routines you expect, and you can also verify
that your program is passing the parameters to these routines
correctly. API tracing can also aid you HP Support Representative
in analyzing application specific problems you may encounter.
Installation changes:
---------------------
Because OTS now resides in the kernel, updating a system with OTS
now requires the regeneration of hp-ux and rebooting the system.
Chapter 2 in the "Installing and Adminstering OTS" discusses
this in detail.
General Requirements:
o S700 must be running HP-UX 8.07 or greater, earlier releases
are not supported.
o S300/400 must be running HP-UX 8.0 or greater.
o S8x7 must be running HP-UX 8.02 or greater.
o Other S800 must be running HP-UX 8.0.
System Requirements:
o 16MB memory
o 30MB free disk space
Potential regen/config conflicts:
OTS installation requires the replacement of some existing
libraries, as well as some other files used in kernel generation.
This is primarily the result of the fact that Streams is not part of
the original 8.0 delivery.
In general non-MR products which require kernel regeneneration
and which modify the /etc/master file may cause conflicts which
can only be corrected by manually modifying /etc/master. The
symptoms of the conflict will be errors during the kernel
generation, or failure of the product to work in the resulting
kernel.
The customization for the following non 8.0 MR products has been
aligned with OTS to avoid these conflicts:
- Netware
- SNA Plus (streams based)
The kernel libraries which are replaced are described on page 2-5 of
the "Installing and Administering OTS" manual. In addition the
following libraries are replaced for the S800:
libhp-ux.a
libmirror.a
libswitch.a
Installing patches for the replaced libraries may cause problems
for OTS. Contact the response center for information about
the suitability of a particular patch.
Configuration Changes
---------------------
The kernelized OTS provides "dynamic SAP mount." This means that
configuration of local Session and Transport addresses is no
longer required. Instead local selectors are assigned on an as
needed basis when an application (including X.400) registers
with the stack. Specifically the configuration files "ss_user_app"
and "tp_user_app" used in older versions no longer exist.
Also new is improved ability to control facilities information
for destination systems reached via CONS. Previously information
such as reverse charging, Call User Groups, etc. were configured on
a per subnetwork basis, meaning that all end systems reached
through that subnetwork were treated the same. Now this information
can be customized for each destination system.
In addition more control over the CONS X.25 behavior is provided,
including ability to select whether X.25 binds by PID and the use
of fast select.
Some other changes are the ability to control the size of the routing
tables (it was fixed size) and the use of interface names rather
than device file names for LAN based subnetworks.
Configuration of up to two LAN cards is supported. Each card
must be associated with a distinct subnetwork.
Many of the parameters for OTS are now dynamically configurable,
meaning that they can be changed while the stack is running.
The new command otsupdate is used to pass modified parameter
values to OTS. See the discussion below "Starting/Stopping
the stack" for more information.
Starting/Stopping the Stack
---------------------------
In the previous releases of OTS, the user could issue the "otsstop"
operation in order to halt the operation of the stack. The
typical reason for stopping the stack was to modify configuration
values and then restart the stack (via "otsstart") with the
new values.
With the kernelized OTS, the stack may be started only once. In
order to "stop" the stack, the system must be rebooted. To allow
the user to change configuration without requiring a system
reboot the new command "otsupdate" is provided. This command
will dynamically alter the stacks configuration without taking
the stack down.
Most OTS configuration parameters are dynamic. The parameters which
are not dynamic are subnetwork information. Specifically, new
cards cannot be added underneath a running OTS without rebooting.
Also the local network address cannot be changed without rebooting.
Items which can be changed dynamically are Session, Transport,
and Network layer timers and flags, remote address information,
routing information, and FTAM and MMS parameters.
Chapter 5 in the "Installing and Administering OTS" manual
describes the parameters in detail and indicates whether
they are dynamic.
Conversion of C.01.00 and C.02.00 Configurations
------------------------------------------------
At the time of installation, via update(1M) any existing configuration
files from previous versions will be automatically translated to
support the new version. If you wish to preserve your old
configuration files, you should back them up before product
installation.
Functional Description of New Protocols
---------------------------------------
OSI ROSE and ACSE Services:
These services reside at layer 7 of the OSI Reference Model.
OTS/9000 complies with ISO 9072 parts 1 and 2 (ROSE) and
ISO 8649 and ISO 8650 (ACSE). ROSE supports the invoke,
result, error and reject operations.
OSI Presentation Layer:
The Presentation layer correspondes to layer 6 of the OSI
Reference Model. OTS/9000 complies with ISO 8822/CCITT X.216
and ISO 8823/CCITT X.226. OTS/9000 provides the kernel
functional unit, negotiated release and "normal mode" connections.
Multi-System Distributed System Gateway (MSDSG):
MSDSG addresses issues of interworking between Connection Oriented
(CO) and Connectionless (CL) systems. The functionality is described
in ISO Technical Report 10172 and is refered to as an Active
Transport Layer Relay (ATLR). OTS/9000 provides the ATLR
functionality, so that systems on CO networks may communicate
at the Transport layer and above with systems on CL networks,
using the OTS/9000 node as a relay.